Overview Node-RED Custom Blocks

This reference provides technical specifications for all Overview custom nodes available in the OV20i Node-RED environment. These specialized nodes extend standard Node-RED functionality for vision inspection workflows.

Overview Custom Nodes Architecture

The OV20i includes pre-installed custom nodes designed specifically for machine vision applications. These nodes provide standardized interfaces for inspection operations and ensure compatibility with industrial automation systems.

Node Categories:

• Inspection Logic Nodes - Process and evaluate inspection results
• Data Processing Nodes - Format and transform inspection data
• I/O Control Nodes - Interface with hardware inputs and outputs
• System Control Nodes - Manage camera functions and status

All Block Outputs Node

Purpose and Functionality

The "All Block Outputs" module is a crucial component within the unified pipeline system. It is responsible for outputting data after each camera capture. It collates and processes all AI block data, ensuring the output is comprehensive and detailed.

Functionality

This module outputs data as a JSON object. The data includes information from various AI processes such as inspection, alignment, classification, and segmentation. Each capture's output is meticulously structured to provide valuable insights into the inspection process.

Data Fields

Inspection Data

• Inspection ID: A rolling 16-bit integer that increments for each inspection
• Inspection Time: An ISO 8601 formatted timestamp of the capture for each inspection
• Image URL: An HTTP URL to the captured image (jpg)

Alignment Data

• Success: Indicates whether the part was successfully aligned
• Center Location X: The x-coordinate of the aligned part's center
• Center Location Y: The y-coordinate of the aligned part's center
• Confidence: The confidence level of the alignment (0-1)
• Matched Angle: The angle matched relative to the template

Classification Data

Predictions:

• ROI ID: The ID of the predicted Region of Interest (ROI)
• ROI Name: The name of the predicted ROI
• Confidence: The confidence level of the predicted class (0-1)
• Predicted Class: The name of the predicted class

Segmentation Data

• Confidence Score Threshold: The threshold used to process the segmentation model outputs (0-1)

Blobs:

• Center X: The x-coordinate of the blob's center
• Center Y: The y-coordinate of the blob's center
• Pixel Count: The total pixel count (area) of the blob
• Major Axis Length: The length in pixels of the major axis
• Minor Axis Length: The length in pixels of the minor axis
• ROI ID: The ID of the predicted ROI
• ROI Name: The name of the predicted ROI
• Predicted Class: The name of the predicted class for the blob

Classes:

• Predicted Class: The class name
• Number of Blobs: The number of blobs in the class
• Pixel Count: The total pixel count (area) of all blobs in the class

Classification Block Logic Node

Purpose and Functionality

The "Classification Block Logic" node is designed to set and evaluate rules on classification block outputs. The output of this node is a boolean value (true/false), which depends on whether all rules pass or any rule passes.

Functionality

If no rules are set by default, the output will be true if all inspections return the "pass" class. If any class is not "pass," the output will be false. This node allows for customization through rule setting, enabling more specific criteria to be applied to the classification results.

Key Features

• Allows setting of specific rules on classification block outputs
• Boolean output based on rule evaluation (true/false)
• Default behavior ensures output is true if all inspections return "pass" and false if any do not
• Configurable confidence threshold for more precise rule setting
• No immediate connections to other components, allowing for flexible future integration

Usage Scenarios

• Ensuring consistent quality control by verifying that all inspection outputs meet the defined "pass" criteria
• Customizable rule settings to adapt to various inspection requirements
• Providing clear pass/fail output for automated decision-making processes

Format Data for PLC Node

Purpose and Functionality

The "PLC Format Node" is designed to format block outputs to the default PLC format. This ensures compatibility with various PLC (Programmable Logic Controller) systems by adhering to their specific byte order requirements.

Functionality

This node formats data outputs from blocks, converting them into the appropriate byte order based on the target PLC system. The two main types of byte orders used are:

• Little-endian: Typically used by Allen-Bradley PLCs
• Big-endian: Typically used by Siemens PLCs

By properly formatting the data, the node ensures seamless integration and communication with the respective PLC systems, facilitating accurate and reliable data processing.

Key Features

• Formats block outputs to the default PLC format
• Supports little-endian byte order for Allen-Bradley PLCs
• Supports big-endian byte order for Siemens PLCs
• Ensures compatibility and reliable data exchange with various PLC systems
• Enhances the efficiency and accuracy of automated control processes

Usage Scenarios

• Integrating data outputs from AI and automation systems with Allen-Bradley and Siemens PLCs
• Ensuring proper byte order conversion for accurate data interpretation by PLCs
• Streamlining communication between block outputs and PLCs in industrial automation setups

Final Pass/Fail Output Node

Purpose and Functionality

The "Final Pass/Fail Output Node" is designed to set and store an inspection's final pass/fail state. This node ensures the inspection outcome is clearly defined, communicated, and archived as a boolean value.

Functionality

This node processes the results of an inspection and outputs a boolean value indicating the overall state:

• True: Indicates that the inspection has passed
• False: Indicates that the inspection has failed

This node outputs the pass/fail state and stores the result for future reference and analysis. This node simplifies the decision-making process in automated inspection systems by providing a clear and recorded pass/fail output. It also ensures that all results are archived for traceability and quality control purposes.

Key Features

• Sets and stores the final pass/fail state of an inspection
• Outputs a boolean value: false for fail and true for pass
• Ensures clear and unambiguous communication of inspection results
• Archives inspection results for future reference and analysis
• Enhances the efficiency of automated quality control processes
• Integrates seamlessly with other nodes and components in the inspection system

Usage Scenarios

• Determining and storing the outcome of quality control inspections in manufacturing
• Automating decision-making processes based on inspection results
• Providing a straightforward pass/fail output for integration with downstream systems and processes
• Ensuring traceability and quality control through archived inspection results

Save to Library Node

Purpose and Functionality

The "Capture Save Decision Node" determines whether a captured image should be saved to the library. This node outputs a boolean value to indicate the same decision.

Functionality

This node processes the capture data and outputs a boolean value indicating whether the capture should be saved:

• True: Indicates that the capture should be saved to the library
• False: Indicates that the capture should not be saved

By providing a clear save/no-save decision, this node helps manage storage resources efficiently and ensures that only relevant captures are archived for future use.

Key Features

• Determines whether a capture is saved to the library
• Outputs a boolean value: false for do not save and true for save
• Ensures efficient management of storage resources
• Helps in archiving relevant captures for future reference and analysis
• Integrates seamlessly with other nodes and components in the capture and storage system

Usage Scenarios

• Deciding whether to save captured images during automated inspections
• Managing storage resources by only saving relevant captures
• Providing a straightforward save/no-save output for integration with downstream systems and processes
• Ensuring important captures are archived for traceability and quality control

Capture Metadata Node

Purpose and Functionality

The "Metadata Assignment Node" is designed to set the metadata associated with each capture. This metadata can include information such as a serial number, part number, or other relevant details. The assigned metadata will appear in the library alongside the captured data.

Functionality

This node allows for the addition of metadata to each capture. The metadata is structured as an object with string keys and values that can be strings or numbers. This ensures that each capture is accompanied by important contextual information, making it easier to identify and reference in the future.

Key Features

• Assign metadata to each capture
• Metadata can include serial numbers, part numbers, or other relevant information
• Structured as an object with string keys and string or number values
• Ensures that captures in the library are accompanied by contextual information
• Enhances traceability and identification of captured data
• Capture Metadata is only stored to the library if the Pass\Fail node is present.

Usage Scenarios

• Adding serial numbers, part numbers, or other identifiers to captured images
• Providing additional context and information for captures stored in the library
• Facilitating easier identification and reference of captures during analysis and review
• Integrating metadata with other nodes and components in the capture and storage system

Output Nodes

Purpose and Functionality

The "Digital Output Node" is designed to control the output pins on the M12 connector of the OV20i. The node turns the pins on or off based on boolean values.

Functionality

• True: Turns the pin ON
• False: Turns the pin OFF

Digital Output nodes are straightforward in operation and do not have editable properties, ensuring consistent and reliable performance.

Pin Configuration

Pin #	Pigtail	Description
10	Violet	Output 1
11	Gray/Pink	Output 2

note

There is no pulse configuration from the DO as itself, so you need to add a trigger to create a pulse.

Key Features

• Controls the output pins on the M12 connector of the OV20i
• Boolean values determine the state of the pins (ON/OFF)
• No editable properties, ensuring simplicity and reliability

Usage Scenarios

• Automating control processes by turning specific output pins on or off
• Integrating with other control systems for coordinated operations
• Providing a straightforward interface for digital output control on the OV20i

Input Nodes

Purpose and Functionality

Input nodes read the status of digital inputs on the OV20i's M12 connector, allowing external signals to trigger actions within the Node-RED flow.

Key Features

• Real-time input monitoring
• External equipment integration
• Hardware signal detection

Onboard Status LED Node

Purpose and Functionality

The "Onboard Status LED Node" is designed to control the onboard status LED located on top of the OV20i. This LED can display various colors, including Yellow, Orange, and Green.

Functionality

• True: Turns the LED ON
• False: Turns the LED OFF

This node provides a simple interface for controlling the status LED, making it easy to indicate different statuses or states of the device.

LED Colors

• Yellow
• Orange
• Green

Key Features

• Controls the onboard status LED on the OV20i
• Boolean values determine the state of the LED (ON/OFF)
• Supports multiple LED colors: Yellow, Orange, and Green
• Provides visual indication of device status

Usage Scenarios

• Indicating the operational status of the OV20i
• Providing visual feedback for various system states or alerts
• Enhancing user interface with clear and visible status indicators